Skip to content

Bump version to 0.1.2: 0.1.1 published but the workflow bump push was rejected - #55

Merged
thedavidmeister merged 1 commit into
mainfrom
2026-08-19-version-0-1-2
Aug 19, 2026
Merged

Bump version to 0.1.2: 0.1.1 published but the workflow bump push was rejected#55
thedavidmeister merged 1 commit into
mainfrom
2026-08-19-version-0-1-2

Conversation

@thedavidmeister

@thedavidmeister thedavidmeister commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Restores the release-lifecycle invariant after today's merge train: run 32256792684 successfully published rain-datacontract 0.1.1 to Soldeer (registry timestamp 2026-08-19T13:13:19Z, verified via api.soldeer.xyz), then had its own post-publish bump commit rejected by branch protection (GH006: Protected branch update failed for refs/heads/main). Main therefore still says 0.1.1 while 0.1.1 is published — the next content-changing push would fail the autopublish gate (local == published), which is exactly the #24 disease again.

This commit is the byte-equivalent of what the workflow tried to push: [external.package].version 0.1.1 → 0.1.2 (next unpublished patch).

Sibling context: rain.solmem's main is unprotected, so its identical workflow pushes its bump fine. The push-back-vs-protection policy question is tracked separately; this PR only restores the invariant.

QA

  • Discriminating tests: n/a - release-metadata-only diff; no behavior in this repo changes. Suite green (23/23) on the branch.
  • Mutations applied: n/a - no code changed.
  • Oracle: Soldeer registry API (0.1.1 present, uploaded 13:13:19Z) + the failed run's log (GH006 on the bump push) + the rainix-autopublish bump semantic (version = next unpublished).
  • Category check: restore gate invariant after published-but-unbumped state; covered exactly.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the package release metadata to version 0.1.2.

…kflow's own bump push was rejected by branch protection
@thedavidmeister thedavidmeister self-assigned this Aug 19, 2026
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 380d0a88-b4df-4ee6-b8a6-1172ccd62e0a

📥 Commits

Reviewing files that changed from the base of the PR and between b2b2269 and 1d32792.

📒 Files selected for processing (1)
  • foundry.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Walkthrough

The foundry.toml package version changed from 0.1.1 to 0.1.2. The value is release metadata for rainix-autopublish.

Changes

Release metadata

Layer / File(s) Summary
Package version increment
foundry.toml
The [external.package] version changed from 0.1.1 to 0.1.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 1d327

This localized metadata change updates the package version to 0.1.2 and restores the release-version sequence; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the version update and the release-workflow reason for the change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 2026-08-19-version-0-1-2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@thedavidmeister
thedavidmeister merged commit 4cbac8b into main Aug 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant